Systems and methods for regulating user data traffic in a wireless network

ABSTRACT

Various embodiments described herein aim to ensure that user data transmissions (e.g., small data transmissions that are sent using control plane messages) do not become excessive and stay infrequent, thereby reducing the likelihood of a network overload situation. In one embodiment, an admission control function (ACF) for regulating the transmission of uplink user data is implemented in a wireless communication device (WCD) (e.g., a CIoT device). Such a WCD device may receive from a core serving node (CSN) admittance information (AI) (e.g., parameters, such as thresholds, used by the ACF to regulate the uplink traffic) that is used in performing the admittance control.

TECHNICAL FIELD

Aspects of this disclosure relate to regulating user data traffic in awireless network.

BACKGROUND

Wireless communication devices (WCDs) (e.g., smartphones, tablets,phablets, personal computers, cellular Internet-of-Things (CIoT)devices, machine-to-machine devices, etc.) can be used to wirelesslytransmit user data (a.k.a., “application data”) to a receivingcommunication device (e.g., a server computer, such as an applicationserver) via a wireless network (e.g., a 4G cellular network). Within the3GPP system, user data is distinguishable from control plane data, whichis data that is destined for a control plane protocol layer, such as,for example the Non-Access Stratum (NAS) protocol layer.

It is expected that in the near future many things (e.g., householdappliances, meters, vending machines, cars, buildings, etc.) willinclude WCDs—i.e., the things will be given the capability to wirelesslytransmit data via a wireless network (e.g., a 3GPP 4G cellular network).Such things that have WCD capability are sometimes referred to as“cellular Internet-of-Things (CIoT)” devices or “machine typecommunication (MTC)” devices.

It is expected that when CIoT devices have user data (as opposed tocontrol plane data) to send to another device (e.g., an applicationserver), the amount of the user data will tend to be small. It is alsoexpected that the number of CIoT devices in use will dramaticallyincrease in the near future. Thus, even if the CIoT devices only sendsmall amounts of user data, the total amount of user data sent by all ofthe CIoT devices in a given area (or the total number of messages sentby such devices) could overwhelm the radio access network that servesthat given area. The signaling generated at each data transmissionoccasion could also overwhelm in the radio access network and the corenetwork.

Accordingly, what is desired are systems and methods for regulating thetransmission of user data traffic in a wireless network.

SUMMARY

Some CIoTs are configured to send small amounts of user data byincluding the user data in control plane messages (e.g., Non-AccessStratum (NAS) messages) or as part of control plane resources (e.g.radio resource control (RRC) signaling and S1-AP signaling), as opposedto using user plane resources (e.g., data radio bearers (DRBs) and theS1-U interface) to send the user data. Such CIoT devices can potentiallyoverload a network (e.g., overload a base station of a radio accessnetwork or overload a node in the core network) if the CIoT devices arenot limited in how much or how often they send user data in this way.

The 3^(rd) Generation Partnership Project (3GPP) has specifiedmechanisms to handle situations in which a network overload has alreadyhappened (e.g. back-off mechanisms), but the 3GPP has not specifiedmechanisms to prevent overloads from happening in the first place.

One technique that can be used to prevent overloads from happening isoften referred to as “admission control.” Admission control isfrequently used to regulate user data in Internet Protocol (IP)networks. To date, there has been no reason to use admission control inthe control plane. This disclosure proposes to introduce an admissioncontrol mechanism that can be used for “small data” (i.e., a set of datathat is not more than 200 bytes) in the control plane (the mechanism,however, is also applicable for user plane based small data solutionsand non-small data environments).

Described herein are various embodiments that aim to ensure that userdata transmissions (e.g., small data transmissions that are sent usingcontrol plane messages) do not become excessive and stay infrequent,thereby reducing the likelihood of a network overload situation.

For example, in one embodiment, an admission control function (ACF) forregulating the transmission of uplink user data is implemented in theWCDs (e.g., CIoT devices) themselves. Such a WCD device may receiveadmittance information (e.g., parameters, such as thresholds, used bythe ACF to regulate the uplink traffic) from a core serving node (CSN)(i.e., an apparatus in a network that provides network services to theWCD, such as, for example, an apparatus that implements a MobilityManagement Entity (MME), a serving GPRS support node (SGSN), a CIoTServing Gateway Node (C-SGN)—a C-SGN is a newly proposed logical entitythat supports only the necessary functionality required for CIoT usecases). Additionally (or in the alternative) a network based ACF isimplemented in the CSN. The network based ACF controls downlink and/oruplink user data. It is expected that an ACF being mandatory for WCDs issubject to a mobile terminal conformance testing and approval processbefore being allowed to operate in 3GPP cellular networks.

In some embodiments, there are two alternative ways to handle a WCD thattransmits uplink user data more often than desired: deny transmission orgenerate a charging event when an admission threshold is exceeded.Denying a transmission when an admission threshold has been passed maybe particularly useful for ultra-low complexity devices and low endsubscription plans e.g. a fixed cost for the lifetime of thedevice/subscription or a fixed cost for a certain time period (e.g. oneyear). On the other hand, generating specific charging event allows theoperator to charge extra when an admission threshold has been exceeded.

Advantages

An advantage of embodiments described herein is that they reduce thelikelihood a 3GPP wireless network is overloaded by CIoT devices sendingsmall data. Also, the embodiments can be used in combination with othersolutions for small data transmissions (see e.g., 3GPP TR 23.720 Rel-14v 0.1.0 and 3GPP TR 23.887 Rel-12 v12.0.0). Embodiments also provide asolution where a network operator can configure different subscriptionplans for different CIoT devices based on number of small datatransmissions or packets per time unit, data size, inter-arrival timeand similar. Embodiments enable subscription plans for CIoT devices withreduced costs for charging. One subscription plan could for example be10 small data transmissions per day for 5 years. After that thesubscription cannot be renewed but has to be discarded. This would allowa minimum of administrative costs for the operator e.g. monthly billsmay not be needed. Another advantage of embodiments is that they enforcethe limits of the subscription plans for CIoT devices without any wasteof radio resources. That is, blocking of uplink data is done at thesource in the CIoT device before using any radio resources.

The above and other aspects and embodiments are described below withreference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form partof the specification, illustrate various embodiments.

FIG. 1 illustrates a wireless communication system according to someembodiments.

FIG. 2 is a message flow diagram illustrating a process according tosome embodiments.

FIG. 3 is a message flow diagram illustrating a process according tosome embodiments.

FIG. 4 is a message flow diagram illustrating a process according tosome embodiments.

FIG. 5 is a flow chart illustrating a process according to someembodiments.

FIG. 6 is a flow chart illustrating a process according to someembodiments.

FIG. 7 is a flow chart illustrating a process according to someembodiments.

FIG. 8 is a flow chart illustrating a process according to someembodiments.

FIG. 9 is a flow chart illustrating a process according to someembodiments.

FIG. 10 is a block diagram of a CSN according to some embodiments.

FIG. 11 is a block diagram of a WCD according to some embodiments.

DETAILED DESCRIPTION

FIG. 1 illustrates a wireless communication system 100 according to someembodiments. As shown in FIG. 1, system 100 may include a group of WCDs.In the example shown, the group WCDs consists of CIoT device 101 a, CIoTdevice 101 b, CIoT device 101 c, each of which is capable oftransmitting uplink user data to a node 104 of a radio access network(RAN) (i.e., node 104 is a “RAN node”). Node 104 may be a base station,such as, for example, an evolved NodeB (eNB) or a CIoT base station(C-BS), which is a base station designed to serve only CIoT devices.Node 104 (a.k.a., BS 104) communicates (directly or indirectly) with acore serving node (CSN) 106, which is connected to a packet data network(PDN) (e.g., the Internet) 110, either directly or indirectly (e.g.,indirectly via a PDN gateway (PGW) 109). An application server 120 mayalso be connected to network 110. BS 104 and CSN 106 enable the CIoTdevices 101 to transmit data to and receive data from application server120. For example, CIoT devices 101 may be meters that monitor energyconsumption and application server 120 may be a data collection serverfor collecting the energy consumption information generated by CIoTdevices 101.

As discussed above, there is proposal to allow WCDs (e.g., CIoT devices)to transmit a small amount of uplink user data by including such smalluser data in a control plane message and transmitting the control planemessage to a core network node via a radio access network (RAN), inwhich the core network node will extract the user data from the controlplane message and forward it a node in a PDN (e.g., an applicationserver connected to the Internet). Accordingly, when a CIoT device 101has user data (e.g., energy consumption data) to report to applicationserver 120, the CIoT device 101 may be configured to transmit the datausing control plane signaling. Such a technique can lead to efficientuse of the radio interface between the CIoT device 101 and the BS 104.However, as such data transmissions become more frequent and packetsbecome larger there is an inflection point where using the control planesignaling for passing user data becomes inefficient from a networkresource point of view compared to using a data radio bearer (DRB) totransmit the user data. It is desirable that this inflection point isnot reached. Described herein are embodiments for reducing thelikelihood of reaching this inflection point. The embodiments provide amechanism to ensure that small data transmissions do not becomeexcessive and stay infrequent.

In one embodiment, an admission control function (ACF) for regulatingthe transmission of uplink user data is implemented in the WCDsthemselves. Such a WCD device may obtain (e.g., receive from the CSN orretrieve from local configuration in the WCD, or from the UICC)admittance information (AI) indicating (expressly or implicitly) atleast one condition under which the WCD is admitted to transmit userdata to a radio access network (RAN) node (e.g., information identifyinga threshold to regulate the uplink traffic or information forimplementing a token bucket algorithm, such as, for example, informationidentifying the rate of which tokens should be added to the bucket andthe maximum bucket size). Additionally (or in the alternative) a networkbased ACF is implemented in the CSN. The network based ACF controlsdownlink and/or uplink user data. The network may need to performadmission control on uplink transmissions from a WCD because there maybe cases where a WCD that should itself perform access control does notdo so. Such “non-conformant” WCDs shall not have an advantage comparedto conformant WCDs. In some embodiments, there are two alternative waysto handle a WCD that transmits (or attempts to transmit) uplink userdata more often than desired: deny the transmission or generate acharging event when an admission threshold is exceeded.

Denying a transmission when an admission threshold has been passed maybe particularly useful for ultra-low complexity devices and low endsubscription plans e.g. a fixed cost for the lifetime of thedevice/subscription or a fixed cost for a certain time period (e.g. oneyear). In some embodiment, the charging functions can basically besimplified or completely replaced by admission control for suchsubscriptions/devices. “Simplified” in the sense that traditionalbilling based on the amount of data would not be needed. The“simplification” aspect may be important since the average revenue perdevice (ARPD) would typically be small for CIoT devices, hence the costsfor administrating such devices should be kept to a minimum. Fixed lifetime cost of the CIoT device or fixed cost for a certain time periode.g. one year are examples of what would be much easier to offer for theoperator. On the other hand, in some other embodiments, for devices notbeing at the most extreme low end and where some sort of billing isused, generating specific charging event can allow the operator tocharge extra when an admission threshold has been exceeded. In such acase, the generating of specific charging events is used (instead ofdiscarding out of profile traffic) when excessive traffic has occurredand been registered by the network, which will allow the operator tocharge extra for these events.

The decision whether to discard or generate charging event is preferablyWCD/subscriber specific (i.e. for some low end subscribers excessivedata are discarded and other subscribers can based on subscription planor service level agreement be continued to be served at a highercharge).

In some embodiments, a new subscription parameter from a Home SubscriberServer (HSS) to the CSN can be used to decide if discarding or chargingevent applies for a specific WCD. Such an indication can also beconveyed from an machine-to-machine (M2M) service provider to thenetwork operator by other means e.g. as a parameter in a Service LevelAgreement (SLA). It may also be conveyed as a parameter in serviceexposure signaling from an Application Server via a Service CapabilityExposure Function (SCEF) to the HSS subscription profile or the CSN.

When the CSN has received the parameter it will be stored in the CSN(e.g., in a data storage system 1012 of the CSN) and used by the ACFimplemented in the CSN. The parameter may also be included in admittanceinformation (AI) passed to a WCD device. The ACF in the WCD may then usethis information for more advanced uplink admission control (e.g. onlyconvey a certain number of out of admission profile small data messages,only convey specific categories of small data messages when out ofprofile etc.).

In some embodiments, instead of blocking a WCD from transmitting controlplane signaling containing uplink user data because an uplink user datathreshold has been reached, the WCD can be configured to attempt totransmit user data using non-control plane signaling (e.g., using a dataradio bearer and S1-U).

In some environments, it is primarily the total number of small datatransmission within a certain period of time and not the total amount ofdata transmitted in that period of time that causes high control planesystem load. Accordingly, in some embodiments, the ACF has a focus oncontrolling the total number of small data transmissions within somegiven period of time. In other environments, however, it is primarilythe total amount of data transmitted in a given period of time thatcauses high control plane system load. Thus, in other embodiments, theACF has a focus on regulating the amount of data transmitted (e.g., theamount of data conveyed at each occasion and/or totally over a timeperiod).

Provision of Admittance Information

In some embodiments, the network operator shall be able use differentsubscription plans and flexible setting of the admittance information(AI). In some embodiments, AI for a WCD (or a group of WCDs) is storedin a data base 108 (e.g., a Home Subscriber Server (HSS), as shown inFIG. 1) or in a data base for Service Level Agreements (SLA). The AI mayinclude, for example, a threshold value representing a maximum number ofsmall data transmissions or packets or messages per unit of time (e.g.,day or hour), a maximum data size, an inter-arrival time, etc.

Admission for downlink is checked in the network e.g. MME, C-SGN, or PGWand admission for uplink in both the WCD and in the network e.g. MME,C-SGN, or PGW. The WCD shall check uplink admission to avoid that radioresources become overloaded. The network also needs to check uplinkadmission if a WCD for some reason does not police itself (i.e., is“non-conformant”). Non-conformant terminal implementations shall nothave an advantage compared to conformant terminals.

In some embodiments, the AI is sent to the WCD by the network. The AImay, for example, be passed in an Attach Accept message, in a TAU Acceptmessage, in a Session Creation (create PDN connection) accept/responsemessage, as a PCO parameter, or in other NAS message.

Referring now to FIG. 2, FIG. 2 is a message flow diagram illustrating aprocess according to some embodiments for provisioning AI to a CSN(e.g., MME, C-SGN, gateway, etc.) and a WCD. As shown in FIG. 2:

In step 201, WCD makes an initial attach to the network (e.g., the WCDtransmits an initial NAS message, such as, for example, an AttachRequest).

In step 202, the CSN obtains admittance information. For example, asshown in FIG. 2, the CSN may retrieve the admittance information from adatabase within the network. For instance, in step 202, in response toreceiving an initial NAS message (e.g., Attach Request) transmitted bythe WCD, the CSN may send to the DB 108 a data query including anidentifier for identifying the WCD, which DB, in response to the query,transmits to the CSN subscription information associated with theidentified WCD, which subscription information includes admittanceinformation associated with the WCD.

In step 203, the CSN stores the admittance information locally (e.g. itmay be stored in a Mobility Management (MM) context that is stored in adata storage system 1012 of the CSN or it may be stored onlytemporarily). In addition, the CSN also stores status information (e.g.,counters, timers, etc.) associated with the WCD (or a group of WCDs),which status information is used to perform the downlink (DL) and uplink(UL) admission control with respect to data transmitted by the WCD (orby a WCD included in the group of WCDs). In one embodiment, the AI canalso be provided to the PGW, e.g. as part of the Create Sessionsignaling, and stored and used for admission control in the PGW,particularly admission control of downlink data.

In step 204, the CSN conveys the admittance information (AI) to the WCD.This may be done as part of Attach Accept, TAU Accept, Defaultconnectivity response, other session creation signaling, or as part ofother NAS message to the WCD. When the AI has changed (e.g., the DB orCSN have been updated with new AI) a GUTI Reallocation message may forexample also convey the admittance information.

In step 205, the WCD receives the message containing the AI and storesthe AI locally. In addition the WCD also maintains locally statusinformation (e.g., counters, timers etc.) needed to perform the ULadmission control. In other embodiments, the AI is pre-configured in theuniversal subscriber identity module (USIM) or Universal IntegratedCircuit Card (UICC) of the WCD by the operator of the WCD.

UL Admission Control

As described above, in some embodiments, the WCD 101 shall performadmission control before transmitting any small user data (i.e., a setof user data that is not more than 200 bytes) to the BS 104. Forexample, in some embodiments, the admission control is performed by theWCD before any radio resource control (RRC) signaling is performed tominimize the load on radio resources. The admission control shall beperformed based at least on the status information available in the WCD.Conformance tests shall be able to verify if a CIoT device support thesmall data admission control.

Referring now to FIG. 3, FIG. 3 is a message flow diagram illustratingan UL admission control process. As shown in FIG. 3:

In step 301, a terminal equipment (TE) component of the WCD provides ULuser data (e.g., small user data) to a Mobile Terminal (MT) component ofthe WCD (e.g. over a standardized internal API, see e.g., TS 3GPP TS27.007, or over other implementation specific internal API or interfacewithin or with the WCD).

In step 302, the MT performs admission control based status information(counters, timers) available in the WCD. If the UL user data is notadmitted, the MT shall reject the UL user data transmission request ordiscard the user data depending on device implementation or attempt totransmit the data at a later time. For example, in some embodiments, theMT performs admission control using a conventional token bucketalgorithm. In such embodiments, the status information may include adata transmission value (V) (a.k.a., “bucket value”) (e.g., a counter)that identifies the number of logical “tokens” that are currently in alogical “bucket” and, if V is equal to zero, then the UL user data isnot admitted (i.e., the MT may transmit the UL data), otherwise the ULdata is admitted (i.e., the MT may transmit the UL data). In suchembodiments, the AI may specify that the MT should initially set V at 0or 1 and then periodically increase V by a set amount (e.g., increase Vby 1 every hour) unless V has reached a threshold value (maximum bucketsize) (e.g. 10), in which case the MT should cease incrementing V. Thatis, the AI may specify the rate at which tokens are added to the bucket(e.g., one token per hour) and the maximum bucket size (e.g., 10tokens). In some embodiments, MT should decrement V each time ittransmits user data (or a particular type of user data, such as smalldata). MT may decrement V by 1 for each message that it sends or it maydecrement V based on the size of the message. The amount by which MTdecrements V may also be specified in the AI.

In step 303, after successful admission control the MT sends the UL userdata to the BS.

In step 304, the BS forwards the UL user data to the CSN.

In step 305, the CSN performs admission control based status information(counters, timers) available in the CN node. In some embodiments, if theUL data is not admitted, the UL data is discarded. Further small userdata transmission may be aborted as (e.g. the WCD is moved to idle, andBS informed with appropriate cause code, RRC connection released). Likethe WCD, the CSN may perform admittance control using a toke bucketscheme.

In step 306 a, after successful admission control the CSN forwards theUL user data to the receiving application server. Step 306 a isperformed if CSN includes a PGW that can be used to forward the userdata to a node in the PDN (e.g., the application server) or the WCD is anon-roaming WCD.

In step 306 b, after successful admission control the CSN sends the ULuse data to the PGW. Step 306 b is performed if CSN does not include aPGW or if a separate PGW must be used for the WCD (such as in a roamingsituation).

In step 307, the PGW may be deployed to perform user data admissioncontrol.

In step 308, the PGW forwards the UL user data to the applicationserver.

DL Admission Control

Referring now to FIG. 4, FIG. 4 is a message flow diagram illustrating aDL admission control process. As shown in FIG. 4:

In step 401 a, the application server sends DL data (e.g., DL smalldata) to the PGW for a WCD that uses small data. Step 401 a may beperformed if the CSN does not include a PGW or if a PGW is used in aroaming case or if the application server is unable to communicatedirectly with the CSN.

In step 401 b, the application server sends the DL data to the CSN. Step401 b is performed if the CSN includes a PGW and the application servercan communicate directly with the CSN (e.g. in a non-roaming situation).

In step 402, optionally the PGW may be deployed to perform small dataadmission control. In such a case the PGW may perform admission controlfor DL data (and optionally for both DL data and UL data depending onconfiguration). The admission control in the PGW is based on AI andstatus information (counters, timers) available in the PGW.

In step 403, the PGW forwards the DL data to the CSN.

In step 404, the CSN performs admission control based on AI and statusinformation (counters, timers) available in the CN node. If the DL datais not admitted, the DL data may be discarded. Further small datatransmission shall be aborted as appropriate (depending on solution)e.g. no paging of the WCD done.

In step 405, after successful admission control the CSN conveys the DLdata towards the WCD.

In step 406, the BS receives the DL data transmitted by the CSN andforwards the DL data to the WCD.

In step 407, the MT sends the DL data to the TE or over otherimplementation specific internal API or interface to a receiver withinthe WCD or to a receiver outside the MT or WCD.

FIG. 5 is a flow chart illustrating a process 500, according to someembodiments, that is performed by the WCD.

In step 502, the WCD obtains admittance information (AI) indicating atleast one condition under which the WCD is admitted to transmit userdata to a radio access network (RAN) node. For example, the AI mayindicate that the WCD is admitted to transmit the user data only when a“bucket” includes at least one “token.” That is, for example, the AI mayspecify a rate at which tokens are added to the bucket and the maximumbucket size. In some other embodiments, the AI comprises informationidentifying (expressly or implicitly) a threshold value (T).

In step 504, the WCD initiates the uplink (UL) transmission of user datavia the wireless network. For example, in step 504, the WCD stores theuser data in a transmit buffer.

In step 506, the WCD performs admittance control with respect to theuser data based on the obtained AI. For example, in step 506, the WCDuses the AI (or a bucket defined by the AI) to determine whether the WCDmay at this time transmit the user data to the BS.

In some embodiments, performing the admittance control includes the WCDusing the status information maintained by the WCD (e.g., informationrelating to previously transmitted user data, such as, the abovementioned data transmission value (V)) to determine whether the WCD mayat this time transmit the user data to the RAN node. In someembodiments, in response to determining that the WCD may not at thistime transmit the user data to the RAN node, the WCD i) discards theuser data or ii) transmits the user data at a later point in time.

In some embodiments, prior to performing step 506, the WCD determineswhether the user data qualifies as small data and performs step 506 onlyif the user data is small data, otherwise the WCD transmits the userdata using, for example, a DRB.

FIG. 6 is a flow chart illustrating a process 600, according to someembodiments, that is performed by the WCD.

In step 602, the WCD obtains admittance information (AI) which includesinformation identifying (expressly or implicitly) a threshold value (T),which could be a maximum bucket size value or other threshold.

In step 604, the WCD stores the obtained AI (e.g., the WCD stores the AIin a data storage system 1112 within the WCD).

In step 606, the WCD stores status information comprising a datatransmission value (V) regarding prior data transmissions made by theWCD via the wireless network (e.g., the WCD stores the statusinformation in data storage system 1112). In some embodiments, Vcorresponds to at least one of: i) a number of wireless datatransmissions made by the WCD, ii) an amount of data transmittedwirelessly by the WCD, or iii) a number of logical tokens within alogical bucket. For example, in some embodiments, the V corresponds to anumber of packets transmitted wirelessly by the WCD. In otherembodiments, V corresponds to a number of small data messagestransmitted wirelessly by the WCD (e.g. V identifies the number of smalldata messages that the WCD wirelessly transmitted within the last unitof time (e.g., day, hour, etc.), or ongoing time interval (e.g. day,hour etc.). In other embodiments, as discussed above, V may be a tokencounter for a token bucket scheme (i.e., V identifies the number oftokens in the bucket).

In step 608, the WCD obtains and stores user data for transmission to anode via the wireless network.

In step 609, the WCD resets V if a new time interval has been entered(e.g., the WCD sets V=0). As one example, the WCD may reset V a certainamount of time (e.g., 1 hour) after the most recent transmission of userdata. In this way, for example, the WCD can ensure that user data istransmitted only once per the time interval (e.g., once per hour). In analternative implementation, the control of the V value may be based on atoken bucket algorithm.

In step 610, the WCD compares V against T. For example, as shown in step610 the WCD determines whether V>T. If V is greater than T, the processproceeds to step 612, otherwise it proceeds to step 614. The V>Tcomparison can be made in different ways, e.g. before increase of V forthe current transmission has been made, or after an increase has beenmade as described in step 615. That is, in some embodiments, step 615 isperformed prior to step 610. In a token bucket algorithm, T may be zero(0) and in step 610 the WCD may determine whether V=T, and, if it does,then proceeds to step 612, otherwise proceed to step 614.

In step 612, the WCD discards the user data or transmits the user dataat a later point in time. In some embodiments, the step of transmittingthe user data at a later point in time comprises one of: a) waiting atleast a certain amount of time, and then, after the amount of time haselapsed, retrying to transmit the user data, b) waiting at least untilthe data transmission value (V) has been reset (e.g., zeroed) and thentransmitting the user data, or c) using a DRB to transmit the user datatogether with other user data that was previously buffered for uplinktransmission.

In step 614, the WCD transmits the user data and in step 615 the WCDupdates V. In some embodiments, the WCD updates V by increasing V by anamount (in other embodiments it decreases V by the amount). In someembodiments the amount is 1 (e.g., V=V+1). In some embodiments,transmitting the user data consists of transmitting N number of packetsor N number of data octets or N number of small data messages, and theamount by which V is increased/decreased is equal to N (e.g., V=V+N). Insome embodiments, transmitting the user data via the wireless networkcomprises the WCD transmitting to the CSN via the BS a control planemessage (e.g., a NAS message) comprising at least a portion of the userdata.

FIG. 7 is a flow chart illustrating a process 700, according to someembodiments, that is performed by the WCD and/or the CSN.

In step 702, the device (i.e., the WCD or the CSN) obtains and storesadmission control information (AI) comprising information identifying(expressly or implicitly) a threshold value (T).

In step 704, the device stores data transmission value (V) regardingprior data transmissions made by the WCD via the wireless network.

In step 706, the device activates a timer to the time interval used foradmission control and initializes the data transmission value (V) (e.g.,set V=0).

In step 708, the device determines whether the timer has expired.

In step 710, in response to determining that the timer has expired, thedevice resets the timer to the time interval used for admission controland reinitializes the data transmission value (V) (e.g., set V=0).

FIG. 8 is a flow chart illustrating a process 800, according to someembodiments, that is performed by the CSN. In step 802, the CSN obtainsadmittance information (AI) indicating at least one condition underwhich the WCD is admitted to transmit or receive user data. In step 804,the CSN stores the obtained AI (e.g., the CSN stores the AI in a datastorage system 1012 in the CSN). In step 806, the CSN receives user datatransmitted by or to the WCD. In step 808, the CSN performs admittancecontrol with respect to the user data using the AI.

In some embodiments, the CSN also status information related to prioruser data transmissions from or to the WCD. In such embodiments, thestep of performing admittance control comprises the CSN using the statusinformation to determine whether a traffic threshold identified by theAI has been exceeded. In some embodiments, in response to determiningthat the traffic threshold has been exceeded, the CSN does one of thefollowing: i) discards the received user data, ii) transmits the userdata to the intended recipient and generates a charging event forexceeding the threshold, or iii) transmits the user data to the intendedrecipient at a later point in time.

FIG. 9 is a flow chart illustrating a process 900, according to suchembodiments, that is performed by the CSN.

In step 902, the CSN obtains admittance information (AI) which includesinformation identifying (expressly or implicitly) a threshold value (T)corresponding to a traffic threshold.

In step 904, the CSN stores the obtained AI (e.g., the CSN stores the AIin data storage system 1012).

In step 906, the CSN stores status information associated with a WCD(e.g., the CSN stores the status information in data storage system1012). In this case, the status information comprises, or consists of, adata transmission value (V) related to prior user data transmission fromor to the WCD. In some embodiments, V corresponds to at least one of: i)a number of wireless data transmissions made by the WCD, ii) an amountof data transmitted wirelessly by the WCD, or iii) a number of logicaltokens within a logical bucket. For example, in some embodiments, Vcorresponds to a number of packets transmitted wirelessly by the WCD(e.g., the number packet transmitted with the last hour, other unit oftime, or ongoing time interval). As another example, in some embodimentsV corresponds to a number of small data messages transmitted wirelesslyby the WCD (e.g. V identifies the number of small data messages that theWCD wirelessly transmitted within the last unit of time (e.g., day,hour, etc.) or ongoing time interval).

In step 908, the CSN receives user data transmitted by or to the WCD. Insome embodiments, as mentioned above, the WCD transmits the user data byencapsulating it within a control plane message (e.g., a NAS message).Thus, in some embodiments, CSN receives the user data by receiving acontrol plane message that contains at least a portion of the user data.

In step 909, the CSN resets V if a new time interval has been entered.

In step 910, the CSN compares V with T. More specifically, in thisexample, the CSN determines if V>T. If V>T is true, then the processproceeds to step 912, otherwise it proceeds to step 918.

In step 912, the CSN determines whether it should transmit the data andgenerate an extra charge. If not, the process proceeds to step 914,otherwise it proceeds to step 916.

In step 914, the CSN discards the user data or transmits the user dataat a later point in time.

In step 916, the CSN generates a charging event and/or stores charginginformation enabling extra charging.

In step 918, the CSN transmits the user data, and in step 920 updates V.In some embodiments, step 920 is performed before step 910.

In some embodiments, the CSN updates V by increasing V by an amount (inother embodiments it decreases V by the amount). In some embodiments theamount is 1 (e.g., V=V+1). In some embodiments, transmitting the userdata consists of transmitting N number of packets or N number of dataoctets or N number of small data messages, and the amount by which V isincreased/decreased is equal to N (e.g., V=V+N). In some embodiments,transmitting the user data comprises the CSN transmitting to the WCD viathe BS a control plane message (e.g., a NAS message) comprising at leasta portion of the user data.

FIG. 10 is a block diagram of an embodiment of CSN 105. As shown in FIG.10, CSN 105 may include: a data processing system (DPS) 1002, which mayinclude one or more processors 1055 (e.g., a general purposemicroprocessor and/or one or more other data processing circuits, suchas an application specific integrated circuit (ASIC), field-programmablegate arrays (FPGAs), and the like); a network interface 1005 for use inconnecting CSN 105 to a network; and a data storage system 1012 forstoring AI, status information and other data, which may include one ormore non-volatile storage devices and/or one or more volatile storagedevices (e.g., random access memory (RAM)). In embodiments where CSN 105includes a general purpose microprocessor, a computer program product(CPP) 1041 may be provided. CPP 1041 includes a computer readable medium(CRM) 1042 storing a computer program (CP) 1043 comprising computerreadable instructions (CRI) 1044. CRM 1042 may be a non-transitorycomputer readable medium, such as, but not limited, to magnetic media(e.g., a hard disk), optical media (e.g., a DVD), memory devices (e.g.,random access memory), and the like. In some embodiments, the CRI 1044of computer program 1043 is configured such that when executed by dataprocessing system 1002, the CRI causes the CSN 105 to perform stepsdescribed above (e.g., steps described above with reference to the flowcharts). In other embodiments, CSN 105 may be configured to performsteps described herein without the need for code. That is, for example,data processing system 1002 may consist merely of one or more ASICs.Hence, the features of the embodiments described herein may beimplemented in hardware and/or software.

FIG. 11 is a block diagram of an embodiment of WCD 101. As shown in FIG.11, WCD 101 may include: a data processing system (DPS) 1102, which mayinclude one or more processors 1155 (e.g., a general purposemicroprocessor and/or one or more other data processing circuits, suchas an application specific integrated circuit (ASIC), field-programmablegate arrays (FPGAs), and the like); a radio transceiver 1105 coupled toan antenna 1122 for use wirelessly transmitting data; and a data storagesystem 1112 for storing AI, status information and other data, which mayinclude one or more non-volatile storage devices and/or one or morevolatile storage devices (e.g., random access memory (RAM)). Inembodiments where WCD 101 includes a general purpose microprocessor, acomputer program product (CPP) 1141 may be provided. CPP 1141 includes acomputer readable medium (CRM) 1142 storing a computer program (CP) 1143comprising computer readable instructions (CRI) 1144. CRM 1142 may be anon-transitory computer readable medium, such as, but not limited, tomagnetic media (e.g., a hard disk), optical media (e.g., a DVD), memorydevices (e.g., random access memory), and the like. In some embodiments,the CRI 1144 of computer program 1143 is configured such that whenexecuted by data processing system 1102, the CRI causes the WCD 101 toperform steps described above (e.g., steps described above withreference to the flow charts). In other embodiments, WCD 101 may beconfigured to perform steps described herein without the need for code.That is, for example, data processing system 1102 may consist merely ofone or more ASICs. Hence, the features of the embodiments describedherein may be implemented in hardware and/or software.

Some embodiments described above may be summarized in the followingmanner:

In one aspect there is provided a first method for regulating user datatraffic in a wireless network. In some embodiments, the method includesa wireless communication device (WCD) (e.g., a Cellular Internet ofThings (CIoT) device) obtaining admittance information (AI) indicatingat least one condition under which the WCD is admitted to transmit userdata to a radio access network (RAN) node. The method further includesthe WCD initiating the uplink (UL) transmission of user data via thewireless network. The method also includes the WCD performing admittancecontrol with respect to said user data based on the obtained AI.

In some embodiments, the method further includes the WCD storing statusinformation relating to previously transmitted user data. In such anembodiment, the step of performing admittance control with respect tosaid user data comprises: the WCD using the status information todetermine whether the WCD may at this time transmit the user data to theRAN node; and, in response to determining that the WCD may not at thistime transmit the user data to the RAN node, the WCD i) discarding theuser data or ii) transmitting the user data at a later point in time. Insome embodiments, the AI comprises information identifying a thresholdvalue (T), the status information comprises a data transmission value(V) corresponding to at least one of: i) a number of wireless datatransmissions made by the WCD, ii) an amount of data transmittedwirelessly by the WCD, or iii) a number of logical tokens within alogical bucket. In some embodiments, the data transmission value (V)corresponds to: a number of packets transmitted wirelessly by the WCD ora number of small data messages transmitted wirelessly by the WCD. Insome embodiments, using the status information to determine whether theWCD may at this time transmit the user data to the node via the wirelessnetwork comprises comparing the data transmission value (V) with thethreshold value (T). In such embodiments, the method further includesupdating V as a result of transmitting the user data.

In some embodiments, the method further comprises, at the later point intime, the WCD using the status information to determine whether the WCDmay at this time transmit the user data to the node via the wirelessnetwork; and in response to determining that the WCD may transmit theuser data via the wireless network, the WCD transmitting the user datavia the wireless network and the WCD increasing said data transmissionvalue (V). In some embodiments, transmitting the user data via thewireless network consisted of transmitting N number of packets or Nnumber of data octets or N number of small data messages, and increasingsaid data transmission value consists of increasing said datatransmission value by N.

In some embodiments, the step of transmitting the user data via thewireless network comprises transmitting a control plane messagecomprising at least a portion of the user data.

In some embodiments, the method also includes resetting the datatransmission value (V) in response to determining that a new timerinterval has been entered.

In some embodiments, the method also includes the WCD transmitting aninitial Non-Access Stratus (NAS) message to a network node. In suchembodiments, the WCD receives a NAS response message transmitted by anetwork node as a result of the network node processing the initial NASmessage. In such embodiments, the NAS response message comprises saidAI, and the WCD obtains said AI from the NAS response message. In someembodiments, the initial Non-Access Stratus (NAS) message is one of anAttach Request message or a Tracking Area Update Request message, andthe NAS response message is one of an Attach Accept message or aTracking Area Update Accept message.

In some embodiments, the method also includes determining whether theuser data type is of a certain type, wherein the step of performingadmittance control is performed as a result of determining that the userdata is of the certain type.

In some embodiments, the step of transmitting the user data at a laterpoint in time comprises one of: a) waiting at least a certain amount oftime, and then, after the predetermined amount of time has elapsed,retrying to transmit the user data, b) waiting at least until V has beenreset and then transmitting the user data, or c) using a Data RadioBearer (DRB) to transmit said user data together with other user datathat was previously buffered for uplink transmission.

In another aspect there is provided a wireless communication device(WCD) for regulating user data traffic. In some embodiments, the WCDincludes a data storage system (DSS); and a data processing system (DPS)coupled to the data storage system. The WCD is configured to: store inthe DSS admittance information (AI) indicating at least one conditionunder which the WCD is admitted to transmit user data to a radio accessnetwork (RAN) node; and perform admittance control with respect to saiduser data based on the obtained AI.

In some embodiments, the WCD is further configured to: store in the DSSstatus information relating to previously transmitted user data. In suchembodiments the WCD is configured to perform admittance control withrespect to said user data by: using the status information to determinewhether the WCD may transmit the user data to the RAN node; anddiscarding the user data or transmitting the user data at a later pointin time in response to determining that the WCD may not transmit theuser data to the RAN node.

In some embodiments, the AI comprises information identifying athreshold value (T) and the status information comprises a datatransmission value (V) corresponding to at least one of: i) a number ofwireless data transmissions made by the WCD, ii) an amount of datatransmitted wirelessly by the WCD, or iii) a number of logical tokenswithin a logical bucket. In such embodiments, using the statusinformation to determine whether the WCD may transmit the user data tothe node via the wireless network comprises comparing the datatransmission value (V) with the threshold value (T). In suchembodiments, the WCD is further configured to update V as a result ofthe WCD transmitting the user data. In some embodiments, the datatransmission value (V) corresponds to: a number of packets transmittedwirelessly by the WCD or a number of small data messages transmittedwirelessly by the WCD.

In some embodiments, the WCD is further configured to employ atransmitter to transmit an initial Non-Access Stratus (NAS) message to anetwork node and receive a NAS response message transmitted by thenetwork node as a result of the network node processing the initial NASmessage. In some embodiments, the NAS response message comprises saidAI, and the WCD obtains said AI from the NAS response message. Theinitial Non-Access Stratus (NAS) message may be one of an Attach Requestmessage or a Tracking Area Update Request message, and the NAS responsemessage may be one of an Attach Accept message or a Tracking Area UpdateAccept message.

In some embodiments, the WCD is further configured to determine whetherthe user data type is of a certain type, wherein the WCD is configuredto perform the admittance control with respect to the user data only ifthe user data is of the certain type.

In another aspect, a second method for regulating user data traffic in awireless network is provided. In some embodiments, the second methodincludes a core serving node (CSN) (e.g., MME, SGW, PGW, C-SGN)obtaining admittance information (AI) indicating at least one conditionunder which the WCD is admitted to transmit or receive user data. Themethod also includes the CSN storing the obtained AI. The method furtherincludes the CSN receiving user data transmitted by the WCD ortransmitted to the WCD by another node, and, in response to receivingthe user data, the CSN performing admittance control with respect to theuser data using the AI.

In some embodiments, the method further includes the CSN storing statusinformation related to prior user data transmission from or to the WCD.In such embodiments, the step of performing admittance controlcomprises: the CSN using the status information to determine whether atraffic threshold has been exceeded; and, in response to determiningthat the traffic threshold has been exceeded, the CSN i) discarding thereceived user data, or ii) transmitting the user data to the intendedrecipient and generating a charging event for exceeding the threshold,or iii) transmitting the user data to the intended recipient at a laterpoint in time.

In some embodiments, the AI comprises information identifying athreshold value (T) corresponding to the traffic threshold, and thestatus information comprises a data transmission value (V) correspondingto at least one of: i) a number of wireless data transmissions made bythe WCD, ii) an amount of data transmitted wirelessly by the WCD, oriii) a number of logical tokens within a logical bucket. In suchembodiments, using the status information to determine whether thetraffic threshold has been exceeded comprises comparing the datatransmission value (V) with the threshold value (T).

In some embodiments, the data transmission value (V) corresponds to: anumber of packets transmitted wirelessly by the WCD or a number of smalldata messages transmitted wirelessly by the WCD.

In some embodiments, the method further includes the CSN receiving viathe RAN second user data transmitted by the WCD, the CSN using thestatus information to determine whether a traffic threshold has beenexceeded in response to receiving the second user data; and the CSNforwarding the second user data to another node and increasing said datatransmission value (V) in response to determining the traffic thresholdhas not been exceeded. In some embodiments, the step of receiving saidsecond user data comprises receiving: N number of packets or N number ofdata octets or N number of small data messages, and the step ofincreasing said data transmission value consists of increasing said datatransmission value by N.

In some embodiments, the method further includes resetting the datatransmission value in response to determining that a new timer intervalhas been entered.

In some embodiments, the step of receiving the user data comprisesreceiving a control plane message (e.g., a NAS message) comprising atleast a portion of the user data.

In some embodiments, the method further includes the CSN receiving aninitial NAS message transmitted by one of the WCDs. In such embodimentsthe method further includes the CSN transmitting an AI request to asubscriber server in response to the initial NAS message and the CSN,after transmitting the AI request, receiving said AI from the subscriberserver. The method further includes the CSN storing the AI andtransmitting the AI to the WCD as part of a NAS response to the initialNAS message.

In some embodiments, the method further includes the CSN receivingdownlink user data addressed to the WCD. In such embodiments, the CSNuses the AI and status information to determine whether a trafficthreshold has been exceeded in response to receiving the downlink userdata. In response to determining that the traffic threshold has beenexceeded, the CSN may either i) discard the received downlink user dataor ii) transmit the downlink user data to the WCD and generate acharging event for exceeding the threshold.

In another aspect, a core serving node (CSN) for regulating user datatraffic is provided. The CSN includes a network interface, a datastorage system (DSS); and a data processing system (DPS) coupled to thenetwork interface and the DSS. The CSN is configured to obtainadmittance information (AI) indicating at least one condition underwhich the WCD is admitted to transmit or receive user data, store theobtained AI, receive user data transmitted by the WCD or transmitted tothe WCD by another node, and perform admittance control with respect tothe user data using the AI in response to receiving the user data.

In some embodiments, the CSN is further configured to store statusinformation related to prior user data transmission from or to the WCD.In such embodiments, the CSN performs the admittance control by: usingthe status information to determine whether a traffic threshold has beenexceeded, and i) discarding the received user data, or ii) transmittingthe user data to the intended recipient and generating a charging eventfor exceeding the threshold, or iii) transmitting the user data to theintended recipient at a later point in time in response to determiningthat the traffic threshold has been exceeded.

In some embodiments, the AI comprises information identifying athreshold value (T) corresponding to the traffic threshold and thestatus information comprises a data transmission value (V) correspondingto at least one of: i) a number of wireless data transmissions made bythe WCD, ii) an amount of data transmitted wirelessly by the WCD or iii)a number of logical tokens within a logical bucket. In such embodiments,the CSN is configured to use the AI and the status information todetermine whether the traffic threshold has been exceeded by comparingthe data transmission value (V) with the threshold value (T).

In some embodiments, the data transmission value (V) corresponds to: anumber of packets transmitted wirelessly by the WCD or a number of smalldata messages transmitted wirelessly by the WCD.

In some embodiments, the CSN is further operable to receive via the RANsecond user data transmitted by the WCD. In response to receiving thesecond user data, the CSN uses the AI and the status information todetermine whether a traffic threshold has been exceeded. In response todetermining the traffic threshold has not been exceeded, the CSNforwards the second user data to another node and increases said datatransmission value (V).

In some embodiments, the CSN is further operable to receive an initialNAS message transmitted by one of the WCDs. The CSN transmits an AIrequest to a subscriber server in response to the initial NAS message.The CSN receives said AI from the subscriber server after transmittingthe AI request. The CSN stores the AI after receiving the AI from thesubscriber server. The CSN transmits the AI to the WCD as part of a NASresponse to the initial NAS message.

In some embodiments, the CSN is further operable to receive downlinkuser data addressed to the WCD. The CSN uses the AI and statusinformation to determine whether a traffic threshold has been exceededin response to receiving the downlink user data. Also, the CSN either i)discards the received downlink user data or ii) transmits the downlinkuser data to the WCD and generates a charging event for exceeding thethreshold in response to determining that the traffic threshold has beenexceeded.

While various embodiments of the present disclosure are describedherein, it should be understood that they have been presented by way ofexample only, and not limitation. Thus, the breadth and scope of thepresent disclosure should not be limited by any of the above-describedexemplary embodiments. Moreover, any combination of the above-describedelements in all possible variations thereof is encompassed by thedisclosure unless otherwise indicated herein or otherwise clearlycontradicted by context.

Additionally, while the processes described above and illustrated in thedrawings are shown as a sequence of steps, this was done solely for thesake of illustration. Accordingly, it is contemplated that some stepsmay be added, some steps may be omitted, the order of the steps may bere-arranged, and some steps may be performed in parallel.

The invention claimed is:
 1. A method for regulating user data trafficin a control plane of a wireless network, the method comprising: awireless communication device (WCD) receiving rate control information(RCI) that was transmitted towards the WCD by a core network nodeserving the WCD, the RCI indicating a threshold value (T) for use by theWCD in limiting the rate at which the WCD generates uplink (UL)Non-Access Stratum (NAS) Data messages, the threshold value indicating amaximum number of NAS Data messages per unit of time that the WCD isadmitted to transmit, wherein each NAS Data message is a NAS messagecomprising user data; and based on the received threshold value (T) thatwas transmitted towards the WCD by a core network node serving the WCD,the WCD limiting the rate at which the WCD generates UL NAS Datamessages.
 2. The method of claim 1, further comprising: the WCD storingstatus information relating to previously transmitted NAS Data messages,wherein the step of limiting the rate at which the WCD generates UL NASData messages comprises: the WCD using the status information todetermine whether the WCD may at this time transmit a NAS Data messageto the RAN node; and in response to determining that the WCD may not atthis time transmit the NAS Data message to the RAN node, the WCD i)discarding the user data included in the NAS Data message or ii)transmitting said user data at a later point in time.
 3. The method ofclaim 2, wherein transmitting the user data at a later point in timecomprises waiting at least a certain amount of time, and then, after theamount of time has elapsed, retrying to transmit the user data.
 4. Themethod of claim 2, wherein transmitting the user data at a later pointin time comprises using a Data Radio Bearer (DRB) to transmit said userdata together with other user data that was previously buffered foruplink transmission.
 5. The method of claim 2, wherein transmitting theuser data at a later point in time comprises one of: a) waiting at leasta certain amount of time, and then, after the amount of time haselapsed, retrying to transmit the user data, b) waiting at least until Vhas been reset and then transmitting the user data, or c) using a DataRadio Bearer (DRB) to transmit said user data together with other userdata that was previously buffered for uplink transmission.
 6. The methodof claim 2, wherein the status information comprises a data transmissionvalue (V) corresponding to a number of NAS Data messages that the WCDpreviously transmitted, using the status information to determinewhether the WCD may at this time transmit the NAS Data message comprisescomparing the data transmission value (V) with the threshold value (T),and the method further comprising updating the data transmission value Vas a result of transmitting the NAS Data message.
 7. The method of claim6, further comprising: at the later point in time, the WCD using thestatus information to determine whether the WCD may at this timetransmit a second NAS Data message to the node via the wireless network;and in response to determining that the WCD may transmit the second NASData message via the wireless network, the WCD transmitting the secondNAS Data message via the wireless network and the WCD increasing saiddata transmission value (V).
 8. The method of claim 6, furthercomprising resetting the data transmission value (V) in response todetermining that a new timer interval has been entered.
 9. The method ofclaim 1, further comprising: the WCD transmitting an initial NAS messageto a network node; and the WCD receiving a NAS response messagetransmitted by a network node to the WCD as a result of the network nodeprocessing the initial NAS message, wherein the NAS response messagetransmitted by the network node to the WCD as a result of the networknode processing the initial NAS message comprises said RCI, and the WCDobtains said RCI from the NAS response message, wherein the initial NASmessage is one of an Attach Request message or a Tracking Area UpdateRequest message, and the NAS response message is one of an Attach Acceptmessage or a Tracking Area Update Accept message.
 10. The method ofclaim 1, wherein the WCD is a Cellular Internet of Things (CIoT) device.11. A wireless communication device (WCD) for regulating user datatraffic, the WCD comprising: a data storage system (DSS); and a dataprocessing system (DPS) coupled to the data storage system, wherein theWCD is configured to: store in the DSS rate control information (RCI)received from a core network node, the RCI indicating a threshold value(T) for use by the WCD in limiting the rate at which the WCD generatesuplink (UL) Non-Access Stratum (NAS) Data messages, the threshold valueindicating a maximum number of NAS Data messages per unit of time thatthe WCD is admitted to transmit, wherein each NAS Data message is a NASmessage comprising user data; and based on the received threshold value,limit the rate at which the WCD generates UL NAS Data messages.
 12. TheWCD of claim 11, wherein the WCD is further configured to: store in theDSS status information relating to previously transmitted NAS Datamessages, wherein the WCD is configured to limit the rate at which theWCD generates UL NAS Data messages by performing a process comprising:using the status information to determine whether the WCD may at thistime transmit a NAS Data message; and discard the user data included inthe NAS Data message or transmit said user data at a later point in timein response to determining that the WCD may not at this time transmitthe NAS Data message.
 13. The WCD of claim 12, wherein the statusinformation comprises a data transmission value (V) corresponding to anumber of NAS Data messages that the WCD previously transmitted, usingthe status information to determine whether the WCD may transmit the NASData message comprises comparing the data transmission value (V) withthe threshold value (T), and the WCD is further configured to update Vas a result of the WCD transmitting the NAS Data message.
 14. The WCD ofclaim 13, wherein the data transmission value (V) corresponds to: anumber of packets transmitted wirelessly by the WCD or a number of smalldata messages transmitted wirelessly by the WCD.
 15. The WCD of claim11, wherein the WCD is further configured to: employ a transmitter totransmit an initial NAS message to a network node; and receive a NASresponse message transmitted by the network node to the WCD as a resultof the network node processing the initial NAS message, wherein the NASresponse message transmitted by the network node to the WCD comprisessaid RCI, and the WCD obtains said RCI from the NAS response message,wherein the initial Non-Access Stratus (NAS) message is one of an AttachRequest message or a Tracking Area Update Request message, and the NASresponse message is one of an Attach Accept message or a Tracking AreaUpdate Accept message.
 16. A method for regulating user data traffic ina wireless network, the method comprising: a core serving node (CSN)obtaining admittance information (AI) indicating a threshold value foruse in regulating Non-Access Stratum (NAS) traffic transmitted by awireless communication device (WCD) or addressed to the WCD, thethreshold value representing a maximum number of NAS Data messages perunit of time that the WCD is admitted to transmit or receive, whereineach NAS Data message is a NAS message comprising user data; the CSNstoring the obtained AI; the CSN receiving a NAS Data messagetransmitted by the WCD or transmitted to the WCD by another node; and inresponse to receiving the NAS Data message, the CSN performing admissioncontrol for regulating the received NAS Data message using the obtainedthreshold value.
 17. The method of claim 16, further comprising, the CSNstoring status information related to prior user data transmissions fromor to the WCD, wherein the step of performing admission controlcomprises: the CSN using the status information to determine whether thethreshold value has been exceeded; and in response to determining thatthe threshold value has been exceeded, the CSN i) discarding the userdata included in the received NAS Data message, or ii) transmitting theNAS Data message to the intended recipient and generating a chargingevent, or iii) transmitting the user data to the intended recipient at alater point in time.
 18. The method of claim 16, wherein the NAS Datamessage was transmitted to the CSN by the WCD, the status informationcomprises a data transmission value (V) corresponding to a number of NASData messages that the WCD previously transmitted, and using the statusinformation to determine whether the threshold value has been exceededcomprises comparing the data transmission value (V) with the thresholdvalue (T).
 19. The method of claim 18, further comprising: the CSNreceiving via the RAN a second NAS Data message transmitted by the WCD;in response to receiving the second NAS Data message, the CSN using thestatus information to determine whether the threshold value has beenexceeded; and in response to determining the threshold value has notbeen exceeded, the CSN forwarding the second NAS Data message to anothernode and increasing said data transmission value (V).
 20. The method ofclaim 18, further comprising resetting the data transmission value inresponse to determining that a new timer interval has been entered. 21.The method of claim 16, further comprising: the CSN receiving an initialNAS message transmitted by the WCD; the CSN, in response to the initialNAS message, transmitting an AI request to a subscriber server; the CSN,after transmitting the AI request, receiving said AI from the subscriberserver; the CSN, after receiving the AI from the subscriber server,storing the AI; and the CSN, in response to the initial NAS message,transmitting the AI to the WCD as part of a NAS response to the initialNAS message.
 22. The method of claim 16, further comprising: the CSNreceiving a downlink NAS Data message addressed to the WCD; in responseto receiving the downlink NAS Data message, the CSN using statusinformation to determine whether the threshold value has been exceeded;and in response to determining that the threshold value has beenexceeded, the CSN either i) discarding the user data included in the NASData message or ii) transmitting the downlink NAS Data message to theWCD and generating a charging event.
 23. A core serving node (CSN) forregulating user data traffic, the CSN comprising: a network interface; adata storage system (DSS); and a data processing system (DPS) coupled tothe network interface and the DSS, wherein the CSN is configured to:obtain admittance information (AI) indicating a threshold value for usein regulating Non-Access Stratum (NAS) traffic transmitted by a wirelesscommunication device (WCD) or addressed to the WCD, the threshold valuerepresenting a maximum number of NAS Data messages per unit of time thatthe WCD is admitted to transmit or receive, wherein each NAS Datamessage is a NAS message comprising user data; store the obtained AI;receive a NAS Data message transmitted by the WCD or transmitted to theWCD by another node; and in response to receiving the NAS Data message,perform admission control for regulating the received NAS Data messageusing the obtained threshold value.
 24. The method of claim 23, whereinthe CSN is further configured to store status information related toprior user data transmissions from or to the WCD, wherein the CSNperforms the admission control by: using the status information todetermine whether the threshold value has been exceeded; and in responseto determining that the threshold value has been exceeded, i) discardingthe user data included in the received NAS Data message, or ii)transmitting the NAS Data message to the intended recipient andgenerating a charging event, or iii) transmitting the user data to theintended recipient at a later point in time.
 25. The method of claim 23,wherein the status information comprises a data transmission value (V)corresponding to a number of NAS Data messages that the WCD previouslytransmitted, and the CSN is configured to use the status information todetermine whether the threshold value has been exceeded by comparing thedata transmission value (V) with the threshold value (T).
 26. The methodof claim 25, wherein the CSN is further operable to: receive via the RANa second NAS Data message (NDM) transmitted by the WCD; in response toreceiving the second NDM, use the AI and the status information todetermine whether the threshold value has been exceeded; and in responseto determining the threshold value has not been exceeded, forward thesecond NDM to another node and increasing said data transmission value(V).
 27. The method of claim 23, wherein the CSN is further operable to:receive an initial NAS message transmitted by the WCD; transmit an AIrequest to a subscriber server in response to the initial NAS message;receive said AI from the subscriber server after transmitting the AIrequest; store the AI after receiving the AI from the subscriber server;and transmit the AI to the WCD as part of a NAS response to the initialNAS message.
 28. The method of claim 23, wherein the CSN is furtheroperable to: receive a downlink NAS Data message (NDM) addressed to theWCD; use the AI and status information to determine whether thethreshold value has been exceeded in response to receiving the downlinkNDM; and in response to determining that the threshold value has beenexceeded either i) discarding the user data included in the downlink NDMor ii) transmitting the downlink NDM to the WCD and generating acharging event.